home *** CD-ROM | disk | FTP | other *** search
- Path: newsbf02.news.aol.com!not-for-mail
- From: mudsox@aol.com (Mudsox)
- Newsgroups: alt.computer.consultants,comp.edu,comp.lang.basic.misc,comp.lang.c++,comp.lang.misc,comp.lang.pascal.borland,comp.lang.pascal.delphi.misc,comp.misc,comp.os.msdos.programmer,comp.os.os2.programmer.misc,comp.programming
- Subject: Re: Can we do programming without seeing the end user?
- Date: 23 Mar 1996 22:26:06 -0500
- Organization: America Online, Inc. (1-800-827-6364)
- Sender: root@newsbf02.news.aol.com
- Message-ID: <4j2fce$8sk@newsbf02.news.aol.com>
- References: <4j20es$ea8@atlantis.atlantis.actrix.gen.nz>
- Reply-To: mudsox@aol.com (Mudsox)
- NNTP-Posting-Host: newsbf02.mail.aol.com
-
- Should a programmer be intimately involved in the end-user process or
- completely removed to concentrate on the best technical ways to provide
- systems?
-
- I have had experience with both ends of this spectrum, and the most
- effective automation that I have helped create went like this:
-
- 1. The analyst was trained to do the end-user's job.
- 2. The analyst worked with end-user management to eliminate those manual
- processes that had been inherited by the end-user department but no longer
- made any sense.
- 3. The analyst designed and enhanced a system that supported the new,
- streamlined process.
- 4. The analyst had to use the end-product in a production environment.
-
- In short, don't talk to the users, marry them. Unfortunately, I haven't
- seen nearly enough systems designed this way.
-
- My 2 cents.
-
- Chuck
-